                   ============================
                    R E L E A S E    N O T E S
                   ============================

           Qlogic Ethernet Controller CMPI provider for Windows
                 Copyright (c) 2015 Qlogic Corporation
                        All rights reserved.
                         Aug 14, 2015



Version 2.6.19 (Aug 14, 2015)
-----------------------------
   Fixes:
   ======

1. Problem: CQ80868:NX2 CIM Provider does not enumerate the FCode firmware.

   Cause  : FCode Firmware not supported.
	
   Change : Update to include FCode firmware instance when present
            and upgrade.

   Impact : CIM_SoftwareIdentity Enumeration, FCode Firmware Upgrade


2. Problem : CIMPAT Testing failed for CIM_OrdererdComponent enumeration

   Cause   : Same class has been removed for NX1 filtering

   Change  : Added back the class as it contains info for 
             BootConfig Settings for NX2

   Impact  : CIM_OrderedComponent


Version 2.6.18 (Aug 10, 2015)
-----------------------------

   Fixes:
   ======

1. Problem:   
              'cimcli.exe a QLGC_PhysicalAdapter -n root/qlgcnxns -ac CIM_Realizes -i' crashes CIM server
   Cause:
              Broadcom NX1 was detected by provider but failed to get its properties.
   Change:
              Classes are modifed to filter out NX1
   Impact:
              Classes


Version 2.6.17 (July 28, 2015)
-----------------------------

   Fixes:
   ======

1. Problem:   
              Qlogic NXII Provider(Lenovo_T7.12b.4.2) can't enumerate some instance on Windows
   Cause:
              BMAPI.dll was causing conflict
   Change:
              BMAPI is statically linked to provider dll. 
   Impact:
              None


Version 2.6.16 (July 07, 2015)
-----------------------------

   Fixes:
   ======

1. Problem:   
              Qlogic NXII Provider(Lenovo_T7.12b.4.2) can't enumerate some instance on Windows
   Cause:
              libeay32.dll library was causing conflict
   Change:
              removed libeay32.dll library
   Impact:
              None


Version 2.6.15 (May 21, 2015)
-----------------------------

   Fixes:
   ======

1. Rebranding/split application release.


Version 2.4.4 (September 20, 2013)
---------------------------------

   Fixes:
   ======

1. Problem:   ( Cont00069525)
              CIM_PhysicalPackage properties are not following CIM-0002 specification
   Cause:
              Some properties are not according to the CIM-0002 specification.
   Change:
              Added support for required Properties in CIM_PhysicalPackage class.
   Impact:
              CIM_PhysicalPackage properties.



2. Problem:   ( Cont00068469)
              CMPI 2.3.17 does not fill in enumeration values, or update VPD-V0
   Cause:
              Filename parsing is not correct for Nx2 cards.
   Change:
              Corrected Filename to read new VPD-V0 value from file and update
   Impact:
              InstallFromURI method in CIM_softwareInstallationService for VPD-V0 component.


3. Problem:   ( Cont00065776)
              Store vendor firmware release number in NVRAM on controller.
   Cause:
              Filename parsing is not correct for Nx2 cards.
   Change:
              Corrected Filename to read new VPD-V0 value from file and update
   Impact:
              InstallFromURI method in CIM_softwareInstallationService for VPD-V0 component.


Version 2.4.3 (March 15, 2013)
---------------------------------

   Enhancements:
   =============

1. Feature:
              Sync up code changes with Linux provider.
   Change:
              As requested.
   Impact:
              All.


Version 2.4.2 (March 11, 2013)
-----------------------------------

   Fixes:
   ======

1. Problem:   
              Provider crashed while BACS left open running 
              stress test with enable/disable device.
   Cause:
              Enabling/disabling device during test causes 
              unexpected data which was not properly handled.
   Change:
              Handle data properly.
   Impact:
              Get iSCSI session statistics.


Version 2.4.1 (March 1, 2013)
-----------------------------------

Enhancements:
=============

1. Feature:   
              Add Storage Personality configuration.
   Change:
              Changed as requested.
   Impact:
              Device Configuration.


Version 2.4.0 (February 22, 2013)
---------------------------------

   Enhancements:
   =============

1. Feature:
              Sync up code changes with Linux provider.
   Change:
              As requested.
   Impact:
              All.


Version 2.3.15 (February 15, 2013)
---------------------------------

   Enhancements:
   =============

1. Feature:
              Sync up code changes with Linux provider.
   Change:
              As requested.
   Impact:
              All.


Version 2.3.14 (February 13, 2013)
---------------------------------

   Fixes:
   ======

1. Problem:   
              Tcl library was not compiled for thread safe.
   Cause:
              As stated.
   Change:
              Recompile Tcl library.
   Impact:
              All.


Version 2.3.13 (February 08, 2013)
---------------------------------

   Enhancements:
   =============

1. Feature:   
              Some enhancement in firmware upgrade.
   Change:    
              As requested.
   Impact:    
              Firmware upgrade.


Version 2.3.12 (February 1, 2013)
---------------------------------

   Fixes:
   ======

1. Problem:
              WMI Provider crashes on Windows 2008 and 2012.
   Cause:
              Tcl library was too old.
   Change:
              Use new Tcl library.
   Impact:
              All.


Version 2.3.11 (January 25, 2013)
---------------------------------

   Enhancements:
   =============
   1. Request: Update CMPI Windows provider
      Change:
               Use same code base as CMPI Linux Provider 2.3.11. 
      Impact:
               all


Version 1.2.29 (July 13, 2012)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Remove version from InstanceID property of
               CIM_SoftwareIdentity.
      Change:
               As requested.
      Impact:
               CIM_SoftwareIdentity.

   2. Request: Cont00063409
               Expanded return code information for 
               InstallFromURI() method.
      Change:
               Failure detail will be populated in 
               CIM_ConcreteJob.JobStatus.
      Impact:
               Firmware upgrade using InstallFromURI().

   Fixes:
   =====
   1. Problem: Cont00064017
               MBA firmware upgrade on 57712 fails.
      Cause:
               Firmware upgrade for NX2 was not handled 
               correctly.
      Change:
               Fixed problem in handling NX2 firmware upgrade.
      Impact:
               Firmware upgrade for NX2.


Version 1.2.28 (March 7, 2012)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Remove support for MII Register test on  
               57710 family devices.
      Change:
               As requested.
      Impact:
               Diagnostics on 57710 family devices.


Version 1.2.27 (January 21, 2012)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Update CIM Schema.
      Change:
               As requested.
      Impact:
               All.


Version 1.2.26 (January 24, 2011)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Remove support for MAC Loopback test on 57765, 
               5718 or later NX1 devices.
      Change:
               As requested.
      Impact:
               Diagnostics on 57765, 5718, or later NX1 devices.


Version 1.2.21 (September 3, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ43161
               The Combo MBA firmware file with UEFI driver inside
               should not be device specific.
      Change:
               FwUpg will generate the device specific ID according 
               to the underneath NIC and use it for the device ID 
               of the UEFI driver.
      Impact:
               MBA firmware upgrade.
 
   Fixes:
   =====
   2. Problem: CQ42295
               Failed to upgrade Combo MBA firmware file that
               contained only UEFI driver or FCODE.
      Cause:
               FwUpg expected the Combo MBA firmware file always 
               contained the MBA firmware as the first component.
      Change:
               FwUpg will handle the Combo MBA firmware file that
               contained any combination of MBA firmware, UEFI 
               driver, or FCODE.
      Impact:
               MBA firmware upgrade for BCM57710 adapters


Version 1.2.20 (August 19, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: Diagnostic tests are not applicable to 5785 which are 
               not Broadcom PHY.
      Cause:
               Did not filter out non-applicable 5785.
      Change:
               Do not run diagnostic test on 5785 which are not 
               Broadcom PHY.
      Impact:
               CIM_DiagnosticTest.


Version 1.2.19 (July 13, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Add validation logic to match the software identites,
               firmware image file and the device before performing
               firware upgrade/downgrade operations.
      Change:
               Support added.
      Impact:
               Different upgrade operations on NX1 and NX2 devices
               with combination of matching/mis-matching firmware image
               files.               
               
   Fixes:
   =====
   1. Problem: CQ41825
               Extended directory is corrupted after upgrading 
               to the bootcode that is larger than
               the current one.
      Cause:
               The function that used for upgrade bootcode didn't
               support the extended directory entries.
      Change:
               Added the extended directory support in the function.
      Impact:
               BCM5761 NIC upgrade with extended directory entry.               
               
               
Version 1.2.18 (June 26, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Add support for BCM5785 firmware upgrade.
      Change:
               Added 5785 support.
      Impact:
               upgrade firmware for BCM5785.

   Fixes:
   =====
   1. Problem: iSCSI bootcode upgrade for NX1 failed.
      Cause:
               Extra space in parameter caused parsing 
               to fail.
      Change:
               removed extra space.
      Impact:
               upgrade iSCSI firmware for NX1 adapters.


Version 1.2.17 (June 19, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request:
               NX1: Added support to upgrade iSCSI bootcode 
               with Ipv4, IPv6, or both.
      Change:
               Added support to upgrade iSCSI bootcode with
               Ipv4, IPv6, or both.
               Same rule of calling InstallFromURI() as 
               specified earlier for NX2 applies to NX1.
      Impact:
               upgrade iSCSI firmware for NX1 adapters.

   Fixes:
   =====
   1. Problem: CQ42097
               FwUpg was not able to upgrade the MBA firmware 
               without the "Force" option.
      Cause:
               FwUpg has a bug when it tries to get the MBA 
               version from NVRAM for a comparison to the MBA version 
               in the file.
      Change:
               The bug is fixed and FwUpg can get the MBA version 
               from the NVRAM and compare it to the version of 
               the file.
      Impact:
               upgrade MBA firmware for NX2 adapters.


Version 1.2.16 (June 5, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: Added support for upgrading iSCSI firmware with
               ipv4/ipv6/ipv4n6 options for NX2.
      Change:
               When calling InstallFromURI() method to upgrade
               iSCSI firmware, the InstallOptions parameter array
               must contain value 32769, and the corresponding 
               InstallOptionsValues entry must contain either 
               one of "ipv4", "ipv6", or "ipv4n6" to specify 
               the desired iscsi configuration. If this option 
               is not specified when upgrading iscsi firmware, 
               InstallFromURI() method will return error.
      Impact:
               Firmware upgrade for NX2 iscsi.

   Fixes:
   ======
   1. Problem: Firmware upgrade for NX2 devices with the wrong
               image file  will corrupt the device
      Cause:
               Did not verify image before doing fwupg.
      Change:
               Check image and make sure it is the correct type
               before performing firmware upgrade.
      Impact:
               Firmware upgrade for NetXtreme II.


Version 1.2.15 (May 29, 2009)
---------------------------------

   Fixes:
   ======
   1. Problem: Cont00041511 The FwUpg tool can't prg/upg OTP 
               under Windows 7 64-bit system.
      Cause:
               FwUpg has a bug when trying to release
               an allocated buffer during prg/upg OTP content.
      Change:
               FwUpg can now release the allocated buffer 
               correctly.
      Impact:
               FwUpg for OTP.


Version 1.2.14 (May 22, 2009)
---------------------------------

   Fixes:
   ======
   1. Problem: Cont00040658 Unable to upgrade/downgrade 
               5761S bootcode
      Cause:
               Firmware Upgrade did not support 5761S.
      Change:
               Added 5761S firmware upgrade support.
      Impact:
               firmware upgrade.


Version 1.2.13 (April 10, 2009)
---------------------------------

   Fixes:
   ======
   1. Problem: Upgrade OPT firmware using WMI provider may 
               fail/crash.
      Cause:
               Buffer handling problem when trying to backup 
               NVRAM content before upgrade.
      Change:
               Fixed the buffer issue.
      Impact:
               All OTP upgrade on BCM57760/80/90.


Version 1.2.12 (April 9, 2009)
---------------------------------

   Fixes:
   ======
   1. Problem: Get incorrect driver version display in 
               CIM_SoftwareIdentity
      Cause:
               Driver information was obtained from BMAPI, which does 
               not support the new 4 part driver version format.
      Change:
               Get the version from the driver file instead of BMAPI.
      Impact:
               CIM_SoftwareIdentity

   2. Problem: Running firmware upgrade from CIMStudio caused deadlock.
      Cause:
               An object was kept open, blocking other access.
      Change:
               Changed to use static function so there's no need to 
               keep the object open.
      Impact:
               CIM_SoftwareInstallationService


Version 1.2.11 (March 13, 2009)
---------------------------------

   Fixes:
   ======
   1. Problem: Firmware upgrade allows incorrect selfboot image file 
               to be upgraded for 57790.
      Cause:
               Did not validate device ID in image file against the device.
      Change:
               Validate device ID in image file against the device.
      Impact:
               Firmware upgrade

   2. Problem: Firmware upgrade fails to upgrade MBA firmware for 
               57710/57711/57712 adapters in 64-bit system.
      Cause:
               The 64-bit pointer was not handled correctly when upgrading
               the combined MBA firmware.
      Change:
               The 64-bit pointer is handled correctly when upgrading
               the combined MBA firmware.
      Impact:
               Firmware upgrade


Version 1.2.10 (March 6, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: FwUpgrade Support for 57760/57780/57790
      Change:
               Added new chip support. BMAPI version requirement 
               is upgraded to 7.16.0.
      Impact:
               Firmware upgrade


Version 1.2.9 (February 19, 2009)
---------------------------------

   Fixes:
   ======
   1. Problem: When an instance of DiagnosticRecord is deleted, 
               the associations to the record were left dangling.
      Cause:
               Did not remove the corresponding association.
      Change:
               Delete associations when DiagnosticRecord instances 
               are deleted.
      Impact:
               Diagnostics


Version 1.2.8 (January 21, 2009)
---------------------------------

   Fixes:
   ======
   1. Problem: When running Diagnostics, no DiagnosticCompletionRecord 
               if device driver is not loaded.
      Cause:
               Did not generate records if test cannot be started.
      Change:
               Generate record if concrete job is returned by 
               InvokeMethod() with return code 4096.
      Impact:
               Diagnostics


Version 1.2.7 (January 14, 2009)
---------------------------------

   Fixes:
   ======
   1. Problem: Provider hung while unloading.
      Cause:
               Provider was waiting on an event which was never set 
               if UpgradeFW was never run.
      Change:
               The event was used for a thread which is now obsolete
               as a result of optimization, and so it is now removed 
               and no need to wait for such event.
      Impact:
               All

   2. Problem: DiagnosticTest cannot be terminated for package test 
               and looped test.
      Cause:
               Terminate was not updated with the added support of 
               package test and looped test.
      Change:
               Check if there is a terminate request before executing
               each diagnostic.
      Impact:
               CIM_DiagnosticTest

   3. Problem: CIM_ConcreteJob.PercentComplete remains 0 when 
               DiagnosticTest failed.
      Cause:
               Progress was not updated in case of exception.
      Change:
               Update job progress when exception occurs.
      Impact:
               CIM_DiagnosticTest

   Enhancements:
   =============
   1. Request: Support for simultaneous diagnostic test on different 
               port.
      Change:
               Added Support for simultaneous diagnostic test on 
               different port.
      Impact:
               CIM_DiagnosticTest


Version 1.2.5 (December 8, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: Change CIM_ConcreteJob.JobStatus to contain 
               informative information about current job status.
      Change:
               CIM_ConcreteJob.JobStatus to contain the number of
               loops passed / failed in the current diagnostic test.
      Impact:
               CIM_ConcreteJob


Version 1.2.4 (December 3, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: Provider crashed after a diagnostic test failed.
      Cause:
               Test result data structure was unintentionally 
               corrupted during initialization.
      Change:
               Properly initialize data structure.
      Impact:
               CIM_DiagnosticTest


Version 1.2.3 (December 1, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: DiagnosticTest on NetXtreme II devices failed.
      Cause:
               Previous code optimization introduced a bug
               that caused NDIS handles being used for diag.
      Change:
               Fixed error to use the correct VBD handle for 
               NetXtreme II devices.
      Impact:
               CIM_DiagnosticTest / BRCM_NetworkController.

   Enhancements:
   =============
   1. Request: Support Diagnostic Package Test and test Looping.
      Change:
               New instance of CIM_DiagnosticTest is added to 
               perform package test. All available diagnostic 
               tests to the specified device will be executed.
               Looping is supported by CIM_DiagnosticSetting.
               The LoopControl property of CIM_DiagnosticSetting
               indicates the loop control machanism, and currently
               only "Loop Count" (3) is supported. The 
               array-positional corresponding entry in 
               LoopControlParameter indicates the number of times 
               the diagnostic test will be performed. The default
               loop count is 1, and can be overriden by passing an 
               instance of CIM_DiagnosticSetting which contains 
               a different value in LoopControlParameter.
      Impact:
               CIM_DiagnosticTest, CIM_DiagnosticSetting


Version 1.2.2 (October 29, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: Firmware upgrade for NX2 failed when image path 
               contains spaces.
      Cause:
               White spaces in file path breaks Tcl parsing.
      Change:
               Use quotes around file path.
      Impact:
               CIM_SoftwareInstallationService.

   Enhancements:
   =============
   1. Request: InstallFromURI() to return CIM_ConcreteJob instead 
               of being hung during firmware upgrade.
      Change:
               Upon successful parsing of parameters, 
               InstallFromURI() will return immediately with a 
               reference of CIM_ConcreteJob. User can then check 
               for the JobStatus of the CIM_ConcreteJob.
               JobStatus 7 indicates success, while JobStatus 10 
               indicates failure.
               Currently only one firmware upgrade can be performed 
               by the provider at a time.
      Impact:
               CIM_SoftwareInstallationService


Version 1.2.1 (October 24, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: Cimserver crashed when getting associated classes of 
               CIM_SoftwareIdentity.
      Cause:
               Instances of CIM_ServiceAffectsElement was not created 
               properly.
      Change:
               Corrected the bug in creating CIM_ServiceAffectsElement
               instances.
      Impact:
               all.


Version 1.2.0 (October 23, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: Support Software Update Profile
      Change:
               Added CIM_SoftwareInstallationService and 
               CIM_SoftwareInstallationServiceCapability.
               Implemented InstallFromURI() method to 
               perform firmware upgrade. 
               Currently only supports URI as tftp and 
               local file.
      Impact:
               none

   2. Request: CIM_ExtraCapacityGroup is deprecated in the current 
               CIM schema. Need to update teaming implementation 
               with current CIM classes.
      Change:
               CIM_RedundancySet is used instead to represent a 
               Broadcom Team, conforming to Broadcom's Ethernet Port 
               Extension Profile. BRCM_EthernetPort represents both 
               Broadcom and 3rd party NICs.
      Impact:
               Ethernet Port / Teaming


Version 1.1.0 (April 17, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: Conforming to Software Inventory Profile.
      Change:
               Upgraded to CIM schema 2.14.
               Added SoftwareIdentity instance for boot code, 
               and the associations following Software Inventory 
               Profile.
      Impact:
               all

   2. Request: Added GetFirmwareVersion() to BRCM_NetworkController 
               class.
      Change:
               Implemented new function.
      Impact:
               Dependency on BMAPI v7.10.1 for NCSI version.


Version 1.0.9 (January 30, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: Support 57710.
      Change:
               Added 57710 support.
      Impact:
               all

   Fixes:
   ======
   1. Problem: Some properties of BRCM_BASPTeam were empty.
      Cause:
               Properties were not populated.
      Change:
               Set the appropriate property values.
      Impact:
               all.

   2. Problem: "Aborted" error message during unloading of provider if 
               provider lifespan is very short.
      Cause:
               Synchronization was not handled properly when one of the 
               threads exits.
      Change:
               Synchronize properly then thread exits.
      Impact:
               all.


Version 1.0.8 (November 13, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: Memory leak in CMPI Provider.
      Cause:
               Data cleanup was only called in the CMPI Cleanup APIs, 
               causing memory leak if provider is unloaded without calling 
               the Cleanup API.
      Change:
               Call data cleanup in the destructor of global object, so that
               it will be done in the unloading of provider;
      Impact:
               all.


Version 1.0.7 (October 29, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: Unable to get Diagnostic Records after running diagnostic 
               tests on NetXtremeII devices
      Cause:
               There was a bug in serialization and the instances were not 
               serialized. Running diagnostic tests on NetXtremeII devices
               will trigger a device change event, which in turn triggers 
               the provider to refresh. The refreshing of Diagnostic Record
               will delete all the existing instances and then re-create 
               the instances through deserialization. Since Serialization 
               was not successful, there was nothing to be deserialized, 
               so the instances were lost.
      Change:
               Fixed the bug in serialization.
      Impact:
               All

   Enhancements:
   =============
   1. Request: Change the default ResultPersistence of DiagnosticSetting 
               from "persist forever" to "not persist".
      Change:
               Property changed as requested. 
      Impact:
               all


Version 1.0.6 (October 10, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: Cont00031778 - CMPI:  Running diagnostics tests causes 
               test to hang on IBM Athena
      Cause:
               A critical section was remained locked longer than it 
               should be, causing a deadlock triggered when using the 
               latest DSA software which runs diagnostic tests consecutively.
      Change:
               Unlock the critical section as soon as it is done.
      Impact:
               All


Version 1.0.5 (October 4, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: Provider is unable to load on Windows 2K3
      Cause:
               Provider binary was built with /MD instead of /MT option 
               causing it to have a dependency on VC8 libraries.
      Change:
               Changed project file with the correct build option.
      Impact:
               Windows 2K3


Version 1.0.4 (September 14, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request: IBM requesting CMPI provider for to clean up expired objects
               periodically.
      Change:
               Added new thread to clean up expired objects every 5 minutes. 
      Impact:
               all


Version 1.0.3 (August 23, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: BRCM folder created by provider is taking up limited disk space
      Cause:
               BRCM folder is used to store the persisted class instances, and 
               expired objects were not handled.
      Change:
               If DiagnosticSettingData has ResultPersistent set to 0,
               Records will not be persisted. Old ConcreteJob will also 
               be removed when expired
      Impact:
               ConcreteJob, DiagnosticServiceRecord, DiagnosticSettingsRecord 
               and DiagnosticCompletionRecord


Version 1.0.2 (July 16, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem:  
               Interrupt and Loopback tests failed.
      Cause:
               Interrupt test needed driver to be suspended;
               Loopback tests needed FAD sys files.
      Change:
               Suspend driver for Interrupt test;
               FAD sys files included in release
      Impact:
               Interrupt and Loopback tests.



Version 1.0.1 (June 29, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request: IBM requesting CMPI provider for Windows
      Change:
               Initial alpha release of Windows CMPI provider for IBM.
               Requires BMAPI 7.6.12 (included in the package). 
      Impact:
               all
